AtlaSent — GraphQL Query (read-only)

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

Annotations already declare readOnlyHint=true, etc. The description adds behavioral details beyond annotations: body limit 1MB, depth limit 8, single operation enforced server-side, and error behavior for 404. No contradictions.

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 extremely concise, with three sentences that are front-loaded: purpose, technical limits, and error behavior. Every sentence adds essential information without redundancy.

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?

For a read-only GraphQL query tool with no output schema, the description covers purpose, schema fields, limits, and error behavior. Missing details like authentication or rate limiting are partially addressed by annotations (openWorldHint). Adequately complete for the tool's complexity.

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?

Schema coverage is 100%, so the input schema already documents the query and variables parameters. The description provides context about the endpoint and available schema fields (recentEvaluations, activeBundle) but does not add parameter-specific semantics beyond the schema.

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 clearly states the tool runs a read-only GraphQL query against the AtlaSent V2 endpoint, specifying the schema and distinguishing it from sibling tools that handle mutations or other data retrieval methods. The title reinforces 'read-only'.

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?

The description implies usage for read-only GraphQL queries and warns about the 'closed-by-default' feature availability error, but does not explicitly state when to avoid this tool or mention specific alternatives among the extensive sibling list.

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