add_poi

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

Description only states 'add', which aligns with annotations (destructiveHint: false). No additional behavioral context provided (e.g., side effects, authorization needs, or validation 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?

Single sentence is efficient and front-loaded with clear action and resource. Could be slightly expanded for completeness without becoming verbose.

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?

With 14 parameters, no output schema, and low schema coverage, the description is grossly incomplete. It does not inform the agent about required fields, data formats, or expected behavior.

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 low (29%), and description provides no parameter details. Agent cannot infer meaning of parameters like url, city, address1, etc., from the description alone.

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?

Clearly states verb 'Add' and resource 'point-of-interest to the Things-to-Do page', with examples like restaurant or attraction. Distinguishes from sibling tools such as list_pois, remove_poi, update_poi.

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 on when to use this tool versus alternatives. Does not mention prerequisites or context, such as that it's for creating new POIs, not editing existing ones.

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