athena_coordinate_matrix

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose safety and side effects, but it only says 'Return'. While the verb implies a read-only operation, it does not explicitly state that there are no side effects, nor does it disclose any performance, rate, or consistency implications. The term 'holonomy observations' could even suggest recording actions, adding ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler words, listing all relevant outputs compactly. It is not overly long, but the dense jargon may reduce readability. It is appropriately sized for the complexity, though it could benefit from a bit more structure (e.g., separating the core matrix from auxiliary observations).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the tool (multiple technical outputs, an optional parameter, and no output schema), the description only lists what is returned without explaining the meaning of 'chart-to-chart', 'resolved coordinate subset', or 'holonomy observations'. It does not clarify the purpose of the subject_id parameter or provide any examples. This is insufficient for an agent to confidently use the tool in a domain-specific context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has a single optional parameter (subject_id) with no description, and schema description coverage is 0%. The description only says 'for an optional subject', providing minimal meaning about what the parameter does. It does not clarify what a 'subject' is, how it filters or modifies the output, or any format requirements.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear action ('Return') and a specific resource ('full chart-to-chart transform matrix' plus related data), which distinguishes it from generic tools. However, the heavy jargon ('resolved coordinate subset', 'closed transform triangles', 'holonomy observations') may obscure the primary purpose for an agent without domain context, so it is clear but not maximally accessible.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It does not mention any preconditions, exclusions, or relationships to sibling tools such as athena_diffusion_matrix or athena_apply_transform. The only contextual hint is 'for an optional subject', but there is no explanation of when this should be invoked.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.