Get Contexts

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

Annotations already indicate read-only. The description adds that it is a GET request, supports pagination and filtering, and returns pagination metadata. This goes beyond annotations by detailing output structure and behavior.

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 moderately concise but has a redundant sentence about fetching specific records, which conflicts with the first sentence. It could be streamlined to avoid ambiguity.

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 tool has 10 parameters and no output schema, the description should explain return structure more thoroughly. It mentions paginated JSON array and metadata, but misses details about the record fields or filter descriptions.

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 parameters are well-described. The description reiterates required params and pagination, but does not add new meaning beyond the schema. Baseline score applies.

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 it returns markup contexts for a company and project, which is clear. However, it also mentions fetching a specific record by identifier, causing slight confusion. It distinguishes from sibling tools like get_context_by_id by being plural and listing all contexts.

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 it is for listing contexts, but does not explicitly state when to use it over alternatives like get_context_by_id or when not to use it. No exclusion criteria or context for alternatives.

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