get_job_summary

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Get job summary', implying a read operation, but does not confirm idempotency, side effects, or that it returns the current user's summary. No details about data scope or response format.

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 a single sentence, but includes Japanese translation and a full URL which are somewhat extraneous. Could be slightly more concise without losing clarity.

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 annotations, the description is insufficient. It doesn't explain what data the job summary contains (e.g., role, company, description), or whether it returns the user's own summary or someone else's. Siblings like 'update_job_summary' imply mutable state, but no further context is provided.

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?

There are no parameters, so the description need not explain them. However, it adds no value beyond the schema, as it does not clarify what summary is returned (e.g., for the authenticated user only) or any contextual meaning.

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 action ('Get job summary') and the platform (LAPRAS). However, it does not differentiate from sibling tools like 'get_job_detail' or 'search_jobs', leaving ambiguity about what a 'job summary' specifically entails and whether it's personal or job-specific.

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 such as 'get_job_detail' or 'search_jobs'. There is no mention of prerequisites, context, or when not to use it.

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