Personality (pythagorean)

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

The description mentions a 'name' parameter and example request with 'name', but the input schema does not include 'name'. This discrepancy misrepresents the tool's interface. Annotations are fine but the description undermines transparency.

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 short but includes an incorrect example and extraneous parameter. Conciseness is compromised by inaccuracy.

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?

The tool lacks output schema; no description of return values. The presence of location parameters (latitude, longitude, timezoneOffset) is not explained. The description is incomplete for effective agent use.

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 schema descriptions already cover parameters. However, the description introduces a 'name' parameter not in the schema, which is misleading and adds confusion. The example further reinforces this error.

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 verb 'calculate' and resource 'Personality number from consonants of full birth name'. The title and group help distinguish it from sibling numerology tools, but no explicit differentiation from other Pythagorean tools.

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 like other Pythagorean numerology tools or other systems. The example shows name and date, but the context of use is not discussed.

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