gripp_get

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

No annotations provided, so the description must disclose behavioral traits. It only states it retrieves entities and uses an API method, with no mention of read-only nature, authentication needs, rate limits, error behavior, or side effects.

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?

Two sentences with no fluff. The first sentence efficiently conveys the core purpose. The second sentence adds minor context (API method). Could be slightly more descriptive but remains concise.

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 query tool with 3 parameters, nested objects, and no output schema, the description covers the main purpose and capabilities. It does not describe return format or error handling, leaving some gaps in completeness.

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 schema already documents parameters well. The description adds no specific parameter meaning beyond the schema, which is acceptable, but it doesn't compensate for missing output schema details.

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 retrieves Gripp entities with filters, paging, and ordering. It uses a specific verb and resource, and the name and capabilities distinguish it from siblings like gripp_getone (single entity) and gripp_list_entities (entity types).

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 use for listing multiple entities with filters and paging, but does not explicitly guide when to use this tool versus siblings (e.g., gripp_getone for a specific entity). No exclusions or prerequisites are mentioned.

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