monica_photo

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

The description omits the destructive actions (create, update, delete) that are listed in the input schema and fails to mention that delete is irreversible. This misleads the agent about the tool's capabilities 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 extremely short but not effectively concise; it omits essential information and is inaccurate. It does not earn its place as it fails to clarify the tool's purpose.

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 lack of output schema and the presence of multiple actions (including destructive ones), the description is completely inadequate. It does not explain return values, error handling, or use cases.

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?

Although the input schema has 100% coverage and detailed parameter descriptions, the tool description adds no additional meaning. It only mentions 'list, get' despite the schema supporting more actions, causing confusion.

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 'Manage photos. Actions: list, get.' is tautological and vague. It fails to specify what kind of photos or the broader context, and it understates the actual available actions compared to the input schema.

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, nor explanation of the appropriate context for each action. The description does not help the agent choose between monica_photo and siblings.

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